… the driver axis (#4714)

#4245 (PR #4713) put the D-A3 driver axis under the temporal matrix and left a
reusable `live-dialect-matrix.testkit.ts` behind. Two other consumers of the
shared `@objectstack/spec/data` matrices in this package were still pinned to
one engine:

  - `sql-driver-pagination-conformance.test.ts` — `client: 'better-sqlite3'` in
    both describes, over `PAGINATION_CASES` / `PAGINATION_UNORDERED_CASES`;
  - `sql-driver-or-filter.test.ts` — same client, over `FILTER_LOGIC_CASES`,
    with the describe named `(SQLite)`.

The pagination one is the costly pin. Its own head note says the property half
proves nothing on SQLite: twelve rows come back in rowid order every time, so
the partition check passes with or without the tie-breaker. That is a local
fact about one engine, stated as a permanent excuse — on a real server the
property is the half with teeth, which is what objectui#3106 was reported as.

Both files now sweep once per cell of `DIALECT_CELLS` over the same cases,
asserting the same row-id sets cell for cell. Measured on a live PG 16 @
Asia/Shanghai and MariaDB 10.11 @ +08:00 under TZ=America/New_York: 46 tests per
cell, all three cells identical. With `paginationTieBreaker` sabotaged to return
null, the live-postgres cell reports 11 distinct ids over a 12-row walk — one
row served twice, another never — while every sorted case on SQLite stays green.
The cell exists and it bites.

- Table names carry the issue prefix (`os4714_*`); the bare `t` / `task` this
  suite used while SQLite-only would collide with a parallel suite on a shared
  live database and read as a conformance failure.
- `declareUnprovisionedCell` moves into the testkit and the temporal file now
  calls it too, so one definition of the non-vacuity guard serves all three
  matrices: missing URL is a named skip, and a red under
  `OS_EXPECT_LIVE_DIALECT_MATRIX=1` (#4646).
- No server-timezone axis here: nothing in these matrices compares an instant,
  so requiring a non-UTC server would only manufacture reds that say nothing
  about pagination or `$or`.
- The unpaged-unordered read keeps its exact-sequence pin on SQLite only. #4363
  promises the driver adds nothing to that shape, not that the server returns a
  particular order — MySQL hands back InnoDB primary-key order and Postgres its
  heap order, and pinning either would assert the server's plan as our contract.
  The contract half (no ORDER BY emitted) is asserted per dialect.
- No new CI job: `Temporal Conformance (live PG + MySQL)` already runs the whole
  package against both servers.

`@objectstack/spec/data` is consumed, not edited: no case was softened and no
tie-breaker was added to the fixture to keep a dialect green.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015Br2xsJsczFsTR9bvbh2Ny